Data Replication: isDeleted Column Removed from EditHistory Tables

Data Replication

Update: This schema change has been rolled back. We identified that removing the isDeleted column caused reporting issues and query errors for some customers. The original schema is being restored across all environments, and the isDeleted column is being added back to the EditHistory tables. We apologize for the disruption. The section below describes the original change as released; it no longer reflects the current schema.

What's New?

The isDeleted column has been removed from all EditHistory tables in Data Replication. This change supports ongoing work to align the data model with data retention and privacy compliance requirements.

Why Does It Matter?

EditHistory records are permanently deleted rather than soft-deleted, so the isDeleted column was never populated with meaningful data. Removing it simplifies the EditHistory schema and reflects how the system actually behaves.

How Do I Enable It?

If your reports, ETL pipelines, or other integrations reference the isDeleted column on EditHistory tables, update those queries to remove the reference. Since the column was always empty or defaulted to 0, removing it should not affect your data results. Data Replication schemas evolve periodically to support platform enhancements and data privacy compliance, so we recommend designing pipelines to accommodate schema changes and reviewing column references against the current schema from time to time.

This is part of the R2026.7 release. Click here for release calendar details.